Method and apparatus to store initialization and configuration information

ABSTRACT

Briefly, in accordance with an embodiment of the invention, an apparatus and method to store initialization and configuration information is provided. The method may include storing basic input/output system (BIOS) software in a polymer memory. The method may further include copying a first portion of the BIOS software from the polymer memory to a random access memory (RAM) buffer of a memory controller, wherein the RAM buffer has a storage capacity of at least about two kilobytes (KB).

BACKGROUND

In some computing systems, the basic input/output system (BIOS) software may be stored in a flash electrically erasable programmable read-only memory (EEPROM). Flash memory is a relatively expensive memory, and because of this, the amount of memory available for the BIOS software is typically relatively small. Accordingly, due to the space constraint, some existing BIOS software may be limited in terms of its features and functionality.

Thus, there is a continuing need for alternate ways to store BIOS software in a computing system.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The present invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference to the following detailed description when read with the accompanying drawings in which:

FIG. 1 is a block diagram illustrating a computing system in accordance with an embodiment of the present invention;

FIG. 2 is a block diagram illustrating a computing system in accordance with another embodiment of the present invention;

FIG. 3 is a block diagram illustrating a computing system in accordance with another embodiment of the present invention;

FIG. 4 is a block diagram illustrating a computing system in accordance with another embodiment of the present invention; and

FIG. 5 is a flow diagram illustrating a method to store and execute BIOS software in accordance with an embodiment of the present invention.

It will be appreciated that for simplicity and clarity of illustration, elements illustrated in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements are exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals have been repeated among the figures to indicate corresponding or analogous elements.

DETAILED DESCRIPTION

In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the present invention.

In the following description and claims, the terms “include” and “comprise,” along with their derivatives, may be used, and are intended to be treated as synonyms for each other. In addition, in the following description and claims, the terms “coupled” and “connected,” along with their derivatives may be used, and these terms are not intended as synonyms for each other. Rather, in particular embodiments, “connected” may be used to indicate that two or more elements are in direct physical or electrical contact with each other. “Coupled” may mean that two or more elements are in direct physical or electrical contact. However, “coupled” may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other. In addition, in the following description and claims, the term “information” may be used to refer to data, instructions, or code.

FIG. 1 is a block diagram illustrating a computing system 100 in accordance with an embodiment of the present invention. In this embodiment, computing system 100 may include a processor 110, which may include one or more general-purpose or special-purpose processors such as a microprocessor, microcontroller, application specific integrated circuit (ASIC), a programmable gate array (PGA), a digital signal processor (DSP), or the like. Computing system 100 may also be referred to as a computer or data processing system in some embodiments.

Processor 110 may be coupled to a host bus 115. A memory controller hub (MCH) 120, which may be referred to as a memory controller, may also be coupled to host bus 115. A video controller 125 may be coupled to MCH 120 via an Advanced Graphics Port (AGP) bus 130. Video controller 125 may be coupled to a display 135, which may be a cathode ray tube (CRT) display or a liquid crystal display (LCD). The AGP bus 130 may conform to the Accelerated Graphics Port Interface Specification, Revision 2.0, published May 4, 1998, by Intel Corporation, Santa Clara, Calif.

A system memory 140 may be coupled to MCH 120 via a memory bus 145. In addition, a polymer memory 150 may be coupled to MCH 120 via memory bus 145. Although the scope of the present invention is not limited in this respect, system memory 140 may be a relatively fast volatile memory such as, e.g., a static random access memory (SRAM), a dynamic random access memory (DRAM), or a synchronous DRAM (SDRAM).

In one embodiment, polymer memory 150 may be a non-volatile ferroelectric polymer memory that may include an array of ferroelectric memory cells, wherein each cell may include a ferroelectric polymer material located between at least two conductive lines. The conductive lines may be referred to as address lines and may be used to apply an electric field across the ferroelectric polymer material to alter the polarization of the polymer material.

In this embodiment, polymer memory 150 may utilize the ferroelectric behavior of certain materials to retain data in a memory device in the form of positive and negative polarization, even in the absence of electric power. The ferroelectric polarizable material of each cell may contain domains of similarly oriented electric dipoles that retain their orientation unless disturbed by some externally imposed electric force. The polarization of the material characterizes the extent to which these domains are aligned. The polarization can be reversed by the application of an electric field of sufficient strength and polarity. In various embodiments, the ferroelectric polymer material may comprise a polyvinyl fluoride, a polyethylene fluoride, a polyvinyl chloride, a polyethylene chloride, a polyacrylonitrile, a polyamide, copolymers thereof, or combinations thereof.

In an alternate embodiment, polymer memory 150 may be another type of plastic memory such as, for example, a resistive change polymer memory. In this embodiment, the plastic memory may include a thin film of non-volatile polymer memory material sandwiched at the nodes of an address matrix, e.g., a polymer memory material between two address lines. The resistance at any node may be altered from a few hundred ohms to several megohms by applying an electric potential across the polymer memory material to apply a positive or negative current through the polymer material to alter the resistance of the polymer material. Potentially different resistance levels may store several bits per cell and data density may be increased further by stacking layers.

MCH 120 may control the transfer of information within system 100, e.g., between processor 110, MCH 120, system memory 140, and polymer memory 150. That is, MCH 120 may generate control signals, address signals, and data signals that may be associated with write or read operations. MCH 120 may also include a volatile random access memory (RAM) buffer 121 that may be used to read information stored in polymer memory 150, as discussed below. For example, RAM buffer 121 may be used to buffer information read from polymer memory 150 and used to buffer information written to polymer memory 150.

MCH 120 may also be coupled, e.g., via a hub link 155, to an input/output controller hub (ICH) 160 that is coupled to a input/output (I/O) expansion bus 165 and a Peripheral Component Interconnect (PCI) bus 170, as defined by the PCI Local Bus Specification, Production Version, Revision 2.1 dated in June 1995, or alternately a bus such as the PCI Express bus, or another third generation I/O interconnect bus. The I/O expansion bus 165 may be coupled to an I/O controller 175 that controls access to one or more I/O devices 180. Examples of I/O devices 180 may include input devices, such as, e.g., a keyboard and/or mouse. In an alternate embodiment, the I/O controller 175 may be integrated into ICH 160, as may other control functions.

ICH 160 may also be coupled to a storage device 185. In one embodiment, polymer memory 150 may be a relatively large non-volatile disk cache memory adapted to cache information for storage device 185. Storage device 185 may be a mass storage device such as, for example, a disk memory having a storage capacity of at least about one gigabyte (GB). In various embodiments, storage device 185 may be an electromechanical hard disk memory, an optical disk memory, or a magnetic disk memory, although the scope of the present invention is not limited in this respect. In one embodiment, polymer memory 150 may have a storage capacity of at least about 100 megabytes. For example, polymer memory 150 may have a storage capacity of about 500 megabytes (MB). Polymer memory may be block addressable/accessible, although the scope of the present invention is not limited in this respect.

PCI bus 170 may be coupled to various components including, for example, a wireless interface 190, which may be used in certain embodiments to communicate with remote devices. Although not shown in FIG. 1, wireless interface 190 may include, or be coupled to, a dipole or other antenna, along with other components such as, e.g., a wireless transceiver. In various embodiments, wireless interface 190 may be coupled to system 100 via an external add-in card, or an embedded device. In other embodiments wireless interface 190 may be fully integrated into a chipset of system 100.

Although the description makes reference to specific components of the system 100, it is contemplated that numerous modifications and variations of the described and illustrated embodiments may be possible. Computing system may be a portable personal computer (PC) such as, e.g., a notebook or laptop computer capable of wirelessly transmitting information. However, it is to be understood that embodiments of the present invention may be implemented in another wireless device such as, e.g., a cellular phone, a wireless personal digital assistant (PDA) or the like. In such embodiments, a polymer memory in accordance with an embodiment may be coupled to an internal bus which is in turn coupled to a microprocessor and a peripheral bus, which may in turn be coupled to a wireless interface and an associated antenna such as a dipole antenna, helical antenna, global system for mobile communication (GSM) antenna, and the like.

It should also be noted that polymer memory 150 in accordance with another embodiment of the present invention, may also be implemented in non-wireless devices such as, for example, a desktop PC, server, or workstation that is not configured for wireless communication.

FIG. 2 is a block diagram illustrating a computing system 200 in accordance with another embodiment of the present invention. In this embodiment, polymer memory 150 may be implemented using a PCI add-in card coupled to PCI bus 170.

In addition, in an alternate embodiment of computing system 200 that is not shown in the figures, polymer memory 150 may include an integrated polymer memory controller which may include RAM buffer 121 integrated with polymer memory 150. This polymer memory controller may include interface and decode logic that operates as discussed below with reference to FIG. 5.

FIG. 3 is a block diagram illustrating a computing system 300 in accordance with another embodiment of the present invention. In this embodiment, polymer memory 150 may be integrated into a chipset of system 300, e.g., polymer memory 150 may be integrated with MCH 120.

FIG. 4 is a block diagram illustrating a computing system 400 in accordance with another embodiment of the present invention. In this embodiment, polymer memory 150 may be integrated on a motherboard with other components of system 400 or may be an add-in card. In addition, polymer memory 150 may be coupled to MCH 120 via a PCI-Express link 195. PCI-Express link 195 may be a point-to-point link between components in system 400. In an alternate embodiment (not shown), polymer memory 150 may be coupled to ICH 160 via a PCI-Express link. For simplicity, all components of system 400 have not been shown in FIG. 4.

In various embodiments, in addition to being used as a disk cache, polymer memory 150 may also store firmware or boot information such as, for example, basic input/output system (BIOS) software. Firmware may refer to software or programs that are contained permanently in a hardware device.

In the embodiment wherein polymer memory 150 is a block addressable memory, MCH 120 may include decode and/or interface logic that may allow systems 100, 200, 300, or 400 to retrieve and execute BIOS software stored at either an arbitrary or fixed location in polymer memory 150. The BIOS software may be retrieved from polymer memory 150 and may be executed by processor 110 in response to a power-on/start-up or reset event.

In some computing systems, a reset address may be predefined. For example, in a 32-bit processing system having about four gigabytes of address space, the reset address may be 0XFFFFFFF0. MCH 120 may include interface logic or circuitry that may allow a computing system to retrieve and execute BIOS software stored in polymer memory 150 in response to a reset or power-on event.

Turning to FIG. 5, what is shown is a flow diagram illustrating a method 500 to store and execute BIOS software in accordance with an embodiment of the present invention. Method 500 will be described with reference to computing system 100 of FIG. 1. However, as may be appreciated, method 500 may also be implemented using computing systems 200, 300, or 400.

Method 500 may begin with storing basic input/output system (BIOS) software in polymer memory 150 (block 510). The BIOS software may include operating system (O/S) independent, motherboard specific system initialization code that may be executed on system power-up or in response to a reset event, and may initiate loading of the O/S. The BIOS software may include code to do one or all of the following: check the complementary metal oxide semiconductor (CMOS) setup or configuration information; load the interrupt handlers and device drivers; initialize registers and power management; perform the power-on self-test (POST) to verify to that the computing system's components are operational; display system settings; determine which devices are bootable; initiate the bootstrap sequence.

In response to a power-on or reset of system 100, MCH 120 may include logic to copy the initial block(s) of the BIOS software from polymer memory 150 to RAM buffer 121 (block 520). In one embodiment, RAM buffer 121 may be an eight kilobyte (KB) buffer integrated with MCH 120, although the scope of the present invention is not limited in this respect. Smaller or larger size RAM buffers may also be used for RAM buffer 121. For example, RAM buffer 121 may range in size from about 512 bytes to about 64 KB in different applications, although the scope of the present invention is not limited in this respect. RAM buffer 121 may also have a relatively faster access time compared to polymer memory 150, and may be located in a polymer memory controller that may be part of a chipset of system 100 or may be integrated with polymer memory 150.

After the initial portion of the BIOS software is copied to RAM buffer 121, processor 110 may fetch and execute the initial portion of the BIOS software from RAM buffer 121 (block 530). The initial portion of the BIOS may include POST operations to enable processor 110 to subsequently access system memory 140. The initial portion of the BIOS may also include code to copy the remaining portion of the BIOS from polymer memory 150 to system memory 140. In an alternate embodiment, all or part of the initial portion of the BIOS may be copied to system memory 140 and executed from memory 140.

Next, the initial BIOS software may copy the remainder of the BIOS image from polymer memory 150 into system memory 140 (block 540), and continue execution of the remainder of the BIOS software from system memory 140. That is, after the remaining portion of the BIOS software is copied to system memory 140, processor 110 may fetch and execute the remaining portion of the BIOS software from system memory 140 (block 550).

Generally, the polymer memory controller (e.g., MCH 120) may provide a protection function to prevent overwriting of the BIOS software. In this embodiment, during execution of the BIOS software, the copy of the BIOS image in system memory 140 may be protected to prevent overwriting of the BIOS software (block 560). For example, MCH 120 may include inhibit logic to prevent write access to system memory 140 during the execution of the BIOS code. In addition, MCH 120 may include protection logic that may prevent accidental or intentional overwriting of the BIOS image stored in polymer memory 150 (block 570). For example, “write once” or “reset clear” protection operations may be used. In addition, polymer memory 150 may itself include a “block lock” feature to prevent memory accesses (e.g., reading, writing, or erasing) of one or more segments or regions of polymer memory 150. In one example, the BIOS software may be stored in a specific block or sector of polymer memory 150, and polymer memory and/or MCH 120 may include a block lock circuit to prevent writing to this block of polymer memory 150.

In another embodiment, system 100 may be configured to not allow the BIOS image to completely be overwritten as this may make it difficult to update the BIOS. Instead, the BIOS may be overwritten only in controlled circumstances. For example, one method may include updating the BIOS via a chipset feature that allows a portion of polymer memory 150 that stores the BIOS to only be writable when in SMM, thereby allowing BIOS SMM code to validate any writes to polymer memory 150. Another example may include to lock down the appropriate blocks in the firmware hub itself. Unlocking these blocks to make them writable may require a firmware hub reset, which can be done with a processor INIT if the board is designed to support this. The BIOS update may be copied into memory prior to the INIT, and then validated and executed following the processor init. The INIT does not reset the chipset so the memory contents persist.

In an alternate embodiment, polymer memory 150 may have a separate memory controller from system memory 140. The memory controller of polymer memory 150 may be referred to as a polymer memory controller that may include a RAM buffer similar to RAM buffer 121 discussed above.

In some systems, the initialization process may be referred to as the initial program load (IPL). In such systems, polymer memory 150 may store the initial program load (IPL) information.

In addition to storing BIOS software, in other embodiments, polymer memory 150 may store other initialization or configuration information of system 100. For example, polymer memory 150 may store option read only memory (ROM) code, CMOS configuration information, or extended system configuration data (ESCD). Information such as CMOS, option ROM, or ESCD information may be referred to as boot information, although this list may not be comprehensive of all boot information. Other information not listed here may also be considered to be boot information.

Configuration information may generally refer to the specific hardware and software details in terms of devices attached, capacity or capability, and what the system is made up of. CMOS configuration information may refer to the configuration information that may be stored in a relatively small, e.g., 64 bytes, of CMOS RAM. Examples of CMOS configuration information may include user options or preferences, boot sequence information, and information about the type of devices included in the system such as, e.g., floppy drives, hard disk, keyboard, mouse, display, etc. If system 100 is adapted to support plug and play (PnP), then the BIOS software may also read the ESCD for configuration information on existing PnP devices.

In addition, other general purpose non-volatile information may also be stored in polymer memory 150. For example, EFI variables may be stored in polymer memory 150. EFI may refer to the Extensible Firmware Interface (EFI) specification, version 1.10, published Dec. 1, 2002, by Intel Corporation, Santa Clara, Calif. Method 500 may allow the BIOS software to be stored in non-volatile polymer memory 150 and accessed using a predefined reset address from RAM buffer 121 and/or system memory 140, wherein both buffer 121 and memory 140 may have relatively faster access times compared to polymer memory 150.

Method 500 may allow computing systems such as computing systems 100, 200, 300, or 400, that include a polymer memory and not a flash EEPROM, to be “backward compatible.” For example, as discussed above, in one embodiment BIOS software may be stored in a polymer memory and not a flash EEPROM, and the memory controller coupled to the polymer memory may include a relatively small RAM buffer to enable booting a computing system using boot information stored in the polymer memory.

Some computing systems that store BIOS in a flash EEPROM may use a “page” technique to allow access to a larger BIOS area than can be directly addressable in the address range allowed for BIOS. In such a case, if the portions of the BIOS code/data that need to be accessed for some function are not currently addressable, the BIOS may control the mapping of the address ranges of the flash memory device to make other portions addressable. MCH 120 may be modified to map and copy portions of the BIOS polymer memory 150 into a “BIOSpagable” system memory area so that a similar “page” BIOS operation may be implemented in a system that stores BIOS code in a polymer memory.

In various embodiments, computing systems 100 to 400 may be adapted to allow a field upgradable “boot loader” to rewrite the BIOS image in polymer memory 150. In another embodiment, to allow arbitrary portions of polymer memory 150 to be used to hold the BIOS image, some non-volatile (NV) configuration data may be stored in either memory controller 120 or in known, fixed locations of polymer memory 150 that describe where memory controller 120 may find the current BIOS image.

The embodiments discussed above provide methods, apparatuses, and systems to store and execute BIOS software. In the embodiment illustrated in FIG. 2, wherein polymer memory 150 may be implemented as an add-in card coupled to PCI bus 170, the system boot times may be longer compared to the embodiment illustrated in FIG. 3 since code or data fetches from polymer memory 150 in system 200 may have to traverse more bus interfaces. Including polymer memory 150 on the motherboard (e.g., as illustrated in FIGS. 1 and 3) or integrated into a chipset like MCH 120 (e.g., as illustrated in FIG. 3), may reduce system boot times.

In another embodiment of the present invention, a method includes storing initialization or configuration information of a computing system (e.g., systems 100, 200, 300, 400) in a polymer memory (e.g., polymer memory 150). The initialization information may include BIOS information. The configuration information may include boot sequence information and/or Extended System Configuration Data (ESCD).

While certain features of the invention have been illustrated and described herein, many modifications, substitutions, changes, and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention. 

1. A method, comprising: storing basic input/output system (BIOS) software in a polymer memory.
 2. The method of claim 1, further comprising copying a first portion of the BIOS software from the polymer memory to a random access memory (RAM) buffer of a memory controller, wherein the RAM buffer has a storage capacity of at least about 512 bytes.
 3. The method of claim 2, wherein copying a first portion of the BIOS software from the polymer memory occurs in response to a power-on or reset of a system that includes the polymer memory and wherein the first portion of the BIOS software includes power on self test (POST) code and code to copy a second portion of the BIOS software from the polymer memory to a volatile system memory.
 4. The method of claim 2, further comprising copying a second portion of the BIOS software from the polymer memory to a volatile system memory.
 5. The method of claim 4, further comprising preventing writing to the volatile system memory during execution of the BIOS software.
 6. The method of claim 1, wherein the BIOS software is stored in a first portion of the polymer memory and wherein the method further comprises preventing writing to the first portion of the polymer memory.
 7. The method of claim 1, wherein the polymer memory has a storage capacity of at least about 100 megabytes and the polymer memory is a disk cache that caches information for a disk memory having a storage capacity of at least about one gigabyte.
 8. A method, comprising: storing basic input/output system (BIOS) software in a ferroelectric memory.
 9. The method of claim 8, wherein the ferroelectric memory is a polymer memory.
 10. The method of claim 8, wherein the BIOS software is stored in a first portion of the ferroelectric memory and further comprising preventing writing to the first portion of the ferroelectric memory.
 11. A method, comprising: storing basic input/output system (BIOS) software in a resistive change memory.
 12. The method of claim 11, wherein the resistive change memory is a polymer memory.
 13. The method of claim 11, wherein the BIOS software is stored in a first portion of the resistive change memory and further comprising preventing writing to the first portion of the resistive change memory.
 14. A method, comprising: storing firmware in a polymer memory.
 15. The method of claim 14, wherein the firmware is stored in a first portion of the polymer memory and wherein the method further comprises preventing writing to the first portion of the polymer memory.
 16. The method of claim 14, wherein the polymer memory has a storage capacity of at least about 100 megabytes and the polymer memory is a disk cache that caches information for a disk memory having a storage capacity of at least about one gigabyte.
 17. A method, comprising: storing boot information of a computing system in a polymer memory.
 18. The method of claim 17, wherein the boot information includes BIOS information.
 19. The method of claim 17 wherein the boot information includes non-volatile Extensible Firmware Interface (EFI) variables, CMOS configuration information, or extended system configuration data (ESCD).
 20. The method of claim 17, wherein the boot information is stored in a first portion of the polymer memory and wherein the method further comprises preventing writing to the first portion of the polymer memory.
 21. A method, comprising: storing initialization or configuration information of a computing system in a polymer memory.
 22. The method of claim 21 wherein the initialization information includes BIOS information and wherein the configuration information includes non-volatile Extensible Firmware Interface (EFI) variables, boot sequence information or extended system configuration data (ESCD).
 23. The method of claim 21, further comprising retrieving the initialization or configuration information in response to a start-up or reset event of the computing system.
 24. A method, comprising: storing initial program load (IPL) information in a polymer memory.
 25. The method of claim 24, wherein the IPL information is stored in a first portion of the polymer memory and wherein the method further comprises preventing writing to the first portion of the polymer memory.
 26. The method of claim 24, wherein the polymer memory has a storage capacity of at least about 100 megabytes and the polymer memory is a disk cache that caches information for a disk memory having a storage capacity of at least about one gigabyte.
 27. An apparatus, comprising: a polymer memory to store basic input/output system (BIOS) software.
 28. The apparatus of claim 27, further comprising a random access memory (RAM) buffer to buffer information read from the polymer memory and to buffer information written to the polymer memory.
 29. The apparatus of claim 27, wherein the buffer is integrated with the polymer memory.
 30. The apparatus of claim 27, further comprising a memory controller having a buffer coupled to the polymer memory.
 31. The apparatus of claim 27, wherein the memory controller includes circuitry to prevent overwriting of the BIOS software.
 32. The apparatus of claim 27, wherein the polymer memory includes a block lock circuit to prevent writing to a block of the polymer memory that stores the BIOS software.
 33. The apparatus of claim 27, wherein the polymer memory is a ferroelectric memory.
 34. The apparatus of claim 27, wherein the polymer memory is a resistive change memory.
 35. A system, comprising: a disk memory; and a polymer memory coupled to the disk memory to cache information for the disk memory, wherein the polymer memory is adapted to store basic input/output system (BIOS) software.
 36. The system of claim 35, further comprising: a processor coupled to the polymer memory; and a wireless interface coupled to the processor.
 37. The system of claim 35, further comprising a memory controller having a buffer coupled to the polymer memory.
 38. The system of claim 35, wherein the polymer memory has a storage capacity of at least about 100 megabytes (MB) and the disk memory has a storage capacity of at least about one gigabyte (GB).
 39. The system of claim 35, wherein the system is a portable computer. 